Tree preservation zone

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

reference: 2012/005.G1
name: Land to the rear of Pendower Way
tree-preservation-order: undefined
2012/005
tree-preservation-zone-type: group
geometry: MULTIPOLYGON (((-1.669932 54.975701,-1.669952 54.975694,-1.669960 54.975682,-1.669959 54.975668,-1.669942 54.975652,-1.669709 54.975478,-1.669626 54.975412,-1.669551 54.975355,-1.669523 54.975338,-1.669490 54.975313,-1.669479 54.975248,-1.669471 54.975233,-1.669462 54.975223,-1.669453 54.975220,-1.669439 54.975219,-1.669395 54.975222,-1.669370 54.975227,-1.669348 54.975237,-1.669334 54.975250,-1.669322 54.975265,-1.669318 54.975273,-1.669320 54.975282,-1.669342 54.975305,-1.669412 54.975352,-1.669472 54.975398,-1.669513 54.975425,-1.669561 54.975462,-1.669631 54.975511,-1.669785 54.975627,-1.669819 54.975647,-1.669842 54.975666,-1.669864 54.975688,-1.669885 54.975698,-1.669903 54.975703,-1.669915 54.975704,-1.669932 54.975701)))
point: POINT (-1.669617 54.975449)
notes: These data are update live via a feed to NCC's Tree Managament System, EzyTreev
entry-date: 2022-07-01
start-date: 2012-07-30
end-date

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

The reference for the tree preservation order that covers this zone.